Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

Example: creating an SBO

This chapter has discussed two kinds of situations where using an SBO is appropriate:

Where updates from the client span multiple tables in a parent-child relationship.
Where they are in a one-to-one relationship.

You should build an SBO to handle such updates only if both of the following are true:

Fields from both (or all) the tables involved can be changed on the client.
These changes must be made to the database in a single transaction.

In the example you will build an SBO with two SDOs, for Orders and OrderLine records of an Order.